Skip to content

Run unit tests via valgrind to check for memory leaks #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 4, 2020

Conversation

aentinger
Copy link
Contributor

No description provided.

@aentinger aentinger added the type: enhancement Proposed improvement label Jun 4, 2020
@aentinger aentinger self-assigned this Jun 4, 2020
@codecov-commenter
Copy link

codecov-commenter commented Jun 4, 2020

Codecov Report

Merging #131 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #131   +/-   ##
=======================================
  Coverage   97.23%   97.23%           
=======================================
  Files          28       28           
  Lines         975      975           
=======================================
  Hits          948      948           
  Misses         27       27           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 16512d4...6182206. Read the comment docs.

aentinger added 2 commits June 4, 2020 08:18
…ere are memory leaks because otherwise it returns the return code of the software its running
@aentinger aentinger merged commit 03bc13e into master Jun 4, 2020
@aentinger aentinger deleted the use-valgrind branch June 4, 2020 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants